Process hierarchy: levels, examples and how to build one

A process hierarchy organises all of a company’s processes into levels, from the end-to-end value chain at the top down to the instructions people follow every day. It shows how work fits together, who owns each process and where to improve. Building one is the first step in documenting how your business actually runs.

With this article I would like to give you a full guide to a topic and here’s what that means:

Key takeaways

• A process hierarchy sorts processes into levels: value chain, process groups, processes and activities.
• Build it on your value chain, not your organisation chart.
• Start with the 10-30 processes that keep the business running.
• Give every process one owner, as close to the work as possible.
• AI makes analysis easier, but decisions still need owners. The hierarchy shows what you can delegate – to people and to AI.
• Most hierarchies fail because they stop at a diagram, get too vague or too detailed, or live on one person’s laptop.

What is a process hierarchy?

A process hierarchy is a structured overview of every recurring process in your business, arranged from broad to detailed. Think of it as an architectural blueprint for a house. Instead of beams and rafters, it shows the processes that keep your business upright – from how a receptionist takes a call or sends a late payment notice, to how you hire a new head of department.

It complements your organisational chart. The org chart shows how departments and roles relate. The process hierarchy shows how activities relate and how they deliver the outcomes your organisation needs to reach its goals.

You will also hear the term process architecture. The two are often used as synonyms. Strictly, the business process architecture is the overall design – which processes exist and how they connect to strategy – and the process hierarchy is how you structure and navigate it level by level.

	Org chart	Process hierarchy
Shows	Departments, roles, reporting lines	Processes, outcomes, how work connects
Answers	Who reports to whom?	How do we deliver value, and who owns each step?
Cuts across departments	No	Yes – end-to-end processes span several teams
Changes when	You reorganise	You change how work is done

Below is a sample process hierarchy for product development, a snippet from APQC’s Process Classification Framework® (PCF), the most used process framework in the world:

What are the levels of a process hierarchy?

Most process hierarchies use four levels, so readers can zoom in and out. Naming varies between frameworks, but the logic is the same: each level breaks the one above it into smaller pieces of work.

Level	What it holds	Example	Who uses it
L1 – Value chain	End-to-end processes that create value	Order to cash	Management, for strategy and ownership
L2 – Process groups	The major stages inside an end-to-end process	Fulfil order	Process owners, for scope and handovers
L3 – Processes	The step-by-step workflow teams execute	Check inventory and confirm delivery date	Teams, for day-to-day work
L4 – Activities and work instructions	How each step is done: instructions, templates, system guides	Create a credit note in the ERP system	Employees and new hires, for training and execution

APQC’s PCF goes one step further with five levels: category, process group, process, activity and task. Use the framework as a starting point, then name the levels in a way your people recognise. Once the levels are in place, process mapping is how you fill in the flows at level 3 and below.

Process hierarchy example: how Gluu structures its own processes

At Gluu we start with our value chain overview. It links to every critical process:

Each functional group then holds its own processes as building blocks:

Why build a process hierarchy?

The short answer: knowledge beats guesswork. Familiarity breeds blindness. Many managers are so close to the work that they assume everyone knows the game plan as well as they do. A process hierarchy shows what you do well, what could be better, where your blind spots are, where to cut waste and where economic, market or reputational risk could sit.

A well-made process hierarchy helps you define:

• Which processes are core and which are supporting.
• What each process is meant to deliver.
• Who executes and owns it.
• How processes relate to each other.

“Before Gluu, we had no overview of our processes; they were in each department, and there were many questions, both from stores and internally, about how things were done, or who was responsible for the workflows.”

Jeanette Skree Kaltoft, ERP and Retail Consultant, Sport24

A process hierarchy gives employees a common language and a clear view of their responsibilities. It lets you measure and improve processes continuously, and it is the foundation for your standard operating procedures and routines. It also makes compliance easier: when a new regulation lands, you can drill down and check which processes it touches, and change them quickly because you know where they are.

Gluu’s founder, Søren Pommer, explains it in an interview:

Is a process hierarchy only for large companies?

No. Smaller companies often say a process hierarchy makes sense for a complex enterprise but not for them, because everyone can see what is going on. In practice, the tougher the competition, the more it matters that everyone knows who does what, when and how – whatever the size of the company. What differs is scale: an enterprise may need group processes plus local variants, while a small or medium-sized business can often cover everything in 30-200 processes.

Why a process hierarchy matters more with AI

AI makes analysis easier. It can read your documentation, spot bottlenecks and suggest improvements in minutes. What it does not change is decision-making: someone still has to decide what to do, approve it and answer for the outcome.

A process hierarchy is what makes that split work. When every process has a clear place, a defined outcome and a named owner, you know which decisions belong where – and which work you can hand to AI within those boundaries. It gives you a structure for effective delegation, to people and AI agents alike. Without it, AI produces insight that nobody owns. With it, you can put the power of AI to real use.

Can you build a process hierarchy yourself?

Yes. Process hierarchies can become complex, but anyone can learn the fundamentals, and with some planning you can build a professional one in-house.

Depending on your time, enthusiasm and the complexity of the business, you might lead the project yourself or bring in a consultant. If you use a consultant, let them facilitate rather than author. A consultant who builds the hierarchy alone tends to use their own language instead of yours, your people do not recognise their work in it, and nobody takes ownership. That is one of the most common routes to a stale, buried hierarchy.

How to create a process hierarchy in 7 steps

Step 1: Start with the standards and systems you already have

Don’t reinvent the wheel. If you already have a quality management system, transfer its table of contents into the hierarchy format as a first draft. Talk to your IT team too – they may have mapped processes for a systems implementation.

Step 2: Get management’s nod in a strategy workshop

Without management buy-in, the project goes nowhere fast. Ideally management drives it, or someone close to them does. Pull the top team into a half-day offsite workshop with your best facilitator and map the high-level end-to-end flows: how your business model creates value and who is responsible for what. Expect a lively discussion.

Step 3: Focus on the critical processes first

Find the 10 to 30 processes that really matter – the ones that keep the company running. If you try to capture every process at once, you will get lost in the details and lose sight of the essentials.

⇒ Enterprises

Enterprises typically have HQ functions at group level and operate fairly independently at regional or country level. Create common group processes, but give local offices the freedom to describe how they work. In Gluu, subsidiaries can add group processes to their local accounts on an ongoing basis.

⇒ Small and medium-sized businesses

Depending on complexity, SMBs usually have 30-200 processes. Show the end-to-end processes first, since this gives people a quick overview of the business model. Each function can then have its own process groups and build its own processes as building blocks.

Bisnode started exactly this way:

“In connection with starting Lean, we began to create an overview of all our tasks in the company and assign responsibilities, and that was actually our list in relation to which critical processes needed to be described.”

Marianne Mølgaard Christensen, Customer Engagement Manager, Bisnode

Step 4: Assign one owner to each process

Give each critical process a named owner. Some owners are obvious, like department heads; others take some investigation. Assign ownership at the lowest level possible: the person responsible for running the process rather than the department head. You will see higher adoption and less resistance to change, especially if the people who do the work also help map and improve it.

The utility company Verdo put it like this:

“It should be as low in the hierarchy as it makes sense. It should be someone who can still understand and see across. […] But it should not be so high up that it is at director level.”

Mia Blaabjerg, Project Manager Digitalization, Verdo

Verdo also links each process owner to a manager who backs the larger decisions, so an owner close to the work can still push a change through – for example, an agreement with customer service.

Step 5: Choose a format and tool everyone can use

You need a way to visualise the hierarchy and later map each process. Whatever you choose, it must be shared and easy to collaborate on across the company. A hierarchy that lives in one room, or on one or two people’s laptops, ends up dead and forgotten. That is where online platforms such as Gluu come in – see how Gluu does this.

Step 6: Appoint a project manager

When it is time to roll the hierarchy out to the whole company, you need someone to lead it. Choose a person with a broad understanding of the business who can talk to people in the boardroom and on the shop floor.

Step 7: Manage the hierarchy centrally

Involve everyone, but agree on a few administrators who are allowed to change the structure. Central control keeps the hierarchy consistent:

⇒ Process names and outcomes stay consistent

Mixing “Onboard new customer” with “Customer management” confuses people. Use one naming convention:

• Use an imperative verb plus an object: “Approve invoice”, “Onboard new customer”, “Manage processes” (yes, you should have a process for managing processes).
• Avoid team names in process names – processes often outlive the team.
• Be precise, and use the words employees use about their daily work.

⇒ Processes don’t overlap (too much)

Each process needs a clear name and outcome. That sets its scope and keeps overlap down when other people start mapping theirs.

⇒ Processes become easier to link

With the end-to-end overview in place, it is easier to link related processes and see how they hand over to each other – which pays off in the process mapping that follows.

7 reasons process hierarchies go wrong

A process hierarchy is easy to start and easy to abandon. These are the failure patterns we see most often, and how to avoid them.

Mistake	What happens	How to avoid it
1. It goes no further	The hierarchy becomes a pretty diagram on the wall and is never used or updated	Treat it as step one: map the processes, add instructions, then run and improve them
2. It’s too high level	“Marketing, owned by the marketing director” tells nobody anything	Map the critical cross-functional processes and name an owner for each
3. It’s too low level	The team drowns in detail before the critical processes are clear	Start with the processes that add value and serve the core purpose
4. It’s consultant-created	The structure uses the consultant’s language, so employees don’t recognise their work	Let consultants facilitate; your people name and own the processes
5. It uses bad names	Employees can’t relate process names to what they do	Follow one naming convention (see step 7)
6. It’s hard to access	It lives on one workstation and reflects a small group’s view, not reality	Put it on a shared platform where everyone can read and comment
7. The project isn’t managed well	Ownership drifts and the work stalls	Appoint a project manager with authority and a broad view of the business

The last one is not hypothetical. One company we know fired the project manager in charge of its process hierarchy and put a student in charge instead. The outcome was what you would expect. There are no shortcuts: a hierarchy built to tick a box will not give you the results you are after. If you want to build yours on a shared platform from day one, you can try Gluu for free.

What comes after the process hierarchy?

The hierarchy is the first step, not the goal. The value comes when you map the processes in it, add work instructions, and then run and improve them. Together that is your process documentation – and a shared place to keep it is what process documentation software is for. A clear hierarchy also gives people – and increasingly AI assistants – the context to find the right process, owner and instruction quickly.

---

FAQ – Process hierarchy